Information processing apparatus and method thereof

ABSTRACT

An information processing apparatus configured to calculate an in-operation time of an image processing apparatus includes an authentication log acquisition unit configured to acquire an authentication log including information capable of specifying login time and logout time of a login process in the image processing apparatus, a job log acquisition unit configured to acquire a job log including information capable of specifying job start time and job end time of a job processed by the image processing apparatus, and a calculation unit configured to calculate the in-operation time of the image processing apparatus based on a first in-operation period corresponding to a job processing period specified by the job log and a second in-operation period corresponding to a period which does not overlap a job processing period specified from a job log relating to the authentication log, in a login period specified from the authentication log.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to a technique for deriving an in-operation timeof an image processing apparatus (hereinafter, referred to as a device),such as a printer or a multifunction peripheral.

2. Description of the Related Art

Recently, a device operating rate is used for analysis such as optimumdisposition of device and optimum model selection. The operating rate ofthe device and the like shows a rate of a time (in-operation time)during which the device is used to a time during which the device isoperated (for example, working hours). A load state of the device isanalyzed with the operating rate, and an optimum model is selected basedon a result of the analysis and proposed to a customer.

Conventionally, in a calculation function of an operating rate ofdevice, a time during which a device was used was calculated using atime (job processing time) during which a job was processed. The jobprocessing time is calculated by subtracting the job start time from thejob end time based on information of the job start time and the job endtime included in log information collected from the device. The jobprocessing time was used for analysis of a device operating state bycalculating, for example, a total processing time of jobs processedduring a period.

Further, in analysis of an operating rate of a server system of Webapplication, and the like, as a calculating method for an operating rateof the server, the operating rate was calculated using a time (logintime) during which a user was logged in as a time during which theserver was used. The login time is calculated by retaining a loginhistory of the server and subtracting login times from logout times.Then, a total time during which the server was logged in during a periodwas calculated and used for analysis of a server operating state.

In a system discussed in Japanese Patent Application Laid-Open No.06-251218, a job processing time of an image forming apparatus ismeasured by detecting times at which copy operations, such as operationsof keys of an operation panel or setting of documents to a feeder, arestarted and measuring the times from the above times to times at whichcopy processes are ended.

As described above, when an in-operation time and an operating rate of adevice was calculated, a time obtained by cumulating job processingtimes was used as a device in-operation time. However, in that method, atime (in-operation time) until a user issues a job by operating a deviceis not included in an in-operation time. Further, for example, timesrelating to operations, which were not processed as jobs in the devicesuch as operations (browse, edit) of documents stored in a box functionof the device were not measured in addition to the in-operation times.Further, times, during which although operations relating to jobs wereexecuted, issuing of the jobs was canceled and the like, were notmeasured.

Intrinsically, in a calculation of a device in-operation time, it isnecessary to measure all of the times during which a device is used.Accordingly, in the conventional method for calculating the devicein-operation time based on the log information collected from a device,it cannot be said that a proper device in-operation time is calculated.

SUMMARY OF THE INVENTION

The present invention is directed to an information processing apparatuscapable of obtaining an in-operation time nearer to an actual operationusing log information collected by an image processing apparatus for,for example, proper analysis of an operating rate.

According to an aspect of the invention, an information processingapparatus configured to calculate an in-operation time of an imageprocessing apparatus includes an authentication log acquisition unitconfigured to acquire an authentication log including informationcapable of specifying login time and logout time of a login process inthe image processing apparatus, a job log acquisition unit configured toacquire a job log including information capable of specifying job starttime and job end time of a job processed by the image processingapparatus, and a calculation unit configured to calculate thein-operation time of the image processing apparatus based on a firstin-operation period corresponding to a job processing period specifiedby the job log and a second in-operation period corresponding to aperiod which does not overlap a job processing period specified from ajob log relating to the authentication log, in a login period specifiedfrom the authentication log.

Further features and aspects of the present invention will becomeapparent from the following detailed description of exemplaryembodiments with reference to the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of the specification, illustrate exemplary embodiments, features,and aspects of the invention and, together with the description, serveto explain the principles of the invention.

FIG. 1 is a view illustrating a configuration of a device operatingstate analysis system according to a first exemplary embodiment of theinvention.

FIG. 2 is a view illustrating an example of a configuration of acomputer constituting an analysis server and the like.

FIG. 3 is a block diagram illustrating an example of an internalconfiguration a multifunction peripheral.

FIG. 4 is a block diagram illustrating a detailed functionalconfiguration of a host computer.

FIG. 5 is a block diagram illustrating a detailed functionalconfiguration of the analysis server.

FIG. 6 is a block diagram illustrating a detailed functionalconfiguration of the multifunction peripheral.

FIG. 7 is a view illustrating a job log information table.

FIG. 8 is a view illustrating an authentication log information table.

FIG. 9 is a table for storing authentication information of respectiveusers.

FIG. 10 is a flowchart illustrating a flow of analysis processing of anin-operation time according to the first exemplary embodiment of theinvention.

FIG. 11 is a view illustrating a concept of a calculation process of anin-operation time relating to a job process.

FIG. 12 is a view illustrating a concept of the calculation process ofthe in-operation time executed with an authentication log.

FIG. 13 is a flowchart illustrating an in-operation time calculationprocess in step S1505 in FIG. 10.

FIG. 14 is a view illustrating a configuration of an analysis resulttable.

FIG. 15 is a flowchart illustrating an in-operation time additionprocess in step S1507 in FIG. 10.

FIG. 16 is a flowchart illustrating an analysis processing of anin-operation time according to a second exemplary embodiment of theinvention.

FIG. 17 is a view illustrating an authentication route/job type relatingtable.

FIG. 18 is a flowchart illustrating an authentication ID setting processin step S1509 in FIG. 16.

DESCRIPTION OF THE EMBODIMENTS

Various exemplary embodiments, features, and aspects of the inventionwill be described in detail below with reference to the drawings.

FIG. 1 is a schematic view illustrating a configuration of a system foranalyzing a device operating state according to a first exemplaryembodiment of the invention. In FIG. 1, reference numeral 101 denotes ahost computer which is used by a user for generation of image data andvia which the user instructs a print. Reference numerals 102 and 103denote multifunction peripherals for receiving print data from the hostcomputer 101 and the like via a network and executing a print task onactual papers making use of a known print technique such as anelectrophotographic technique or an inkjet technique.

The multifunction peripherals 102 and 103 have functions for readingpaper documents via scanners, copying the paper documents read thereby,converting the read paper documents to image data, and transmitting theimage data by E-mail, facsimile, and the like. Note that, althoughmultifunction peripherals are exemplified here, it is needless to saythat a single-function image processing apparatus (device) which doesnot have a copy function and includes a printer, a scanner, and the likemay be a target device for an operating state analysis. Referencenumeral 104 denotes an analysis server for analyzing operating states ofthe multifunction peripherals 102 and 103. The host computer 101, themultifunction peripherals 102 and 103, and the analysis server 104 areconnected to one another via a network 105 of a known technique such asEthernet so that they communicate one another.

In the exemplary embodiment, although the analysis server 104 isprovided independently of the multifunction peripherals 102 and 103, amodule having the same function may be disposed internally of each ofthe multifunction peripherals 102 and 103. In this case, it isconsidered that the network communication executed between the analysisserver 104 and the multifunction peripherals 102 and 103 is replaced bydelivery of data via a system bus and the like.

FIG. 2 is a view illustrating an example of an internal configuration ofa computer constituting the host computer 101 and the analysis server104. In FIG. 2, reference numeral 200 denotes an entire computer (PC).The PC 200 includes a CPU 201 for executing software stored in a ROM 202or in a large scale storage device 211, for example, a hard disk (HD)and the like. The CPU 201 integrally controls respective devicesconnected to a system bus 204.

Reference numeral 203 denotes a RAM acting as a main memory, a workarea, and the like for the CPU 201. Reference numeral 205 denotes akeyboard control unit (KBDC) for controlling an instruction input from akeyboard (KBD) 209 disposed to the PC 200. Reference numeral 206 denotesa display control unit (DISPC) for controlling a display of a displaymodule (DISPLAY) 210 composed of, for example, a liquid crystal displayand the like. Reference numeral 207 denotes a disk control unit (DKC)for controlling the large scale storage device such as the hard disk(HD) 211 as a large capacity storage device. Reference numeral 208denotes a network interface card (NIC) for bidirectionally transmittingand receiving data to and from other nodes via the network 105.Reference numeral 212 denotes a timer.

FIG. 3 is a block diagram illustrating an example of an internalconfiguration of the multifunction peripheral 102 or 103. In FIG. 3,reference numeral 300 denotes an entire multifunction peripheral. Themultifunction peripheral 300 includes a CPU 301 for executing softwarestored in a ROM 302 or in a large scale storage device 311 of, forexample, a hard disk (HD) and the like. The CPU 301 integrally controlsrespective devices connected to a system bus 304. Reference numeral 303denotes a RAM acting as a main memory, a work area, and the like for theCPU 301. Reference numeral 305 denotes a panel control unit (Panel C)for controlling an instruction input from an operation panel 309disposed to the multifunction peripheral.

Reference numeral 306 denotes a display control unit (DISPC) forcontrolling a display of a display module (DISPLAY) 310 composed of, forexample, a liquid crystal display and the like. Reference numeral 307denotes a disk control unit (DKC) for controlling the hard disk (HD) 311as a large capacity storage device. Reference numeral 308 denotes anetwork interface card (NIC) for transmitting and receiving data to andfrom other nodes via the network 105. Reference numeral 312 denotes ascanner control unit (SCANC) for reading a paper document by controllingan optical scanner 313 disposed to the multifunction peripheral.Reference numeral 314 denotes a printer control unit (PRNC) for printingan actual paper making use of the known print technique such as theelectrophotographic technique and the inkjet technique by controllingthe printer 315 disposed to the multifunction peripheral.

FIG. 4 is a block diagram illustrating a detailed functionalconfiguration of the host computer 101. In FIG. 4, reference numeral 401denotes a printing application for instructing print, and the printingapplication instructs print by transmitting a drawing instruction andthe like to a printer driver 402. The printer driver 402 converts thedrawing instruction and the like received from the printing applicationto print data, i.e., to PDL (Page Description Language), which can beinterpreted by the multifunction peripherals 102 and 103.

Further, when a device authentication is set, the printer driver 402displays a user authentication dialog and requests the user to input auser name and a password for using the multifunction peripheral. Then,the printer driver 402 transmits the input user name and password to amultifunction peripheral of a print destination via the network 105 andrequests an authentication to the multifunction peripheral. Themultifunction peripheral matches the user name with the password by anthe authentication process unit 613 (FIG. 6) to be described below andresponds whether the name is normally authenticated or theauthentication of the name fails to the printer driver 402.

When the authentication of the name fails, the printer driver 402cancels the print. In contrast, when the name is normally authenticated,the printer driver 402 adds the input user name to a print job as jobowner information and generates a print job. Note that when the deviceauthentication is not set to the printer driver 402, the printer driver402 adds the user name logged in the host computer to the print job asthe job owner information and generates the print job.

Subsequently, the printer driver 402 transmits generated print job datato a print job transmission unit 403. The print job transmission unit403 transmits the print job received from the printer driver 402 to themultifunction peripheral. Reference numeral 404 denotes a Web browserfor interpreting HTML data, drawing an image on the display 210,receiving a user manipulation from the keyboard and the like, andtransmitting a request to an HTTP communication unit 405. Note that aWeb shows a World Wide Web, and HTML shows HyperText Markup Language.

Reference numeral 405 denotes an HTTP communication unit for receiving acommunication request from the Web browser 404, communicating with themultifunction peripheral and the like via the NIC 208 using an HTTP orHTTPS protocol and requesting a Web page, and receives Web page data.Note that HTTP shows HyperText Transfer Protocol, and the HTTPS showsHypertext Transfer Protocol over Secure Socket Layer. Note that therespective functional units 401 to 405 described above are realized bythe CPU 201 of the host computer 101, which reads and executes programsstored in the HD 211 and the like of the host computer 101.

FIG. 5 is a block diagram illustrating a detail function configurationof the analysis server 104. In FIG. 5, reference numeral 500 denotes theanalysis server 104 in its entirety. Reference numeral 501 denotes anI/F unit for communicating with the multifunction peripherals 102 and103 via the NIC 208 and the network 105. Reference numeral 502 denotesan analysis processing unit for executing a device operating stateanalysis process based on a job log and an authentication log andrecording a result of analysis to the storage device 211.

Reference numeral 503 denotes a job log collection unit for executing ajob log acquisition process for collecting job log information(illustrated in FIG. 7 to be described below) from the multifunctionperipherals 102 and 103 and storing the job log information in thestorage device 211 of the analysis server 104. Reference numeral 504denotes an authentication log collection unit for executing anauthentication log acquisition process for collecting authentication loginformation (illustrated in FIG. 8 to be described below) from themultifunction peripherals 102 and 103 and storing the authentication loginformation in the storage device 211 of the analysis server 104. Thelog information may be collected by being transmitted from the devicesat a predetermined time or by being requested from the analysis serverside. Note that the respective functional units 501 to 504 are realizedby the CPU 201 of the analysis server 104, which reads and executesprograms stored in the HD 211 and the like of the analysis server 104.

FIG. 6 is a block diagram illustrating a detailed functionalconfiguration of the multifunction peripherals 102 and 103. In FIG. 6,reference numeral 600 denotes an entire multifunction peripheral.Reference numeral 601 denotes an I/F unit connected to the network 105for receiving a print job from the host computer 101. Reference numeral602 denotes a print data storage unit for temporarily storing print jobdata in the RAM 303 and the hard disk (HD) 311. Reference numeral 610denotes a UI control unit for controlling the operation panel 309 viathe panel control unit (Panel C) 305 and receiving a login request tothe multifunction peripheral, a copy instruction, and a scantransmission instruction of the user.

When the UI control unit 610 receives the login request from the user,it transmits the user name, the password, and the like to theauthentication process unit 613 and requests an authentication. When theauthentication process unit 613 is normally authenticated, the UIcontrol unit 610 receives an authentication ID from the authenticationprocess unit 613. Thereafter, the UI control unit 610 retains the username and the authentication ID until it receives a logout request, andwhen the UI control unit 610 is instructed to issue a job such as a copyand the like by the user manipulation, it transmits the user name andthe authentication ID to the job management unit 603 together with a jobissue request. Further, when a logout operation is executed from theoperation panel, the UI control unit 610 executes a logout process.

Further, the UI control unit 610 has “timeout time” as operation setinformation, and when an operation is not executed from the operationpanel in a time set by “timeout time”, the UI control unit 610 executesthe logout process. Note that a set value of “timeout time” can bereferred to also from an external module, for example, from the analysisserver 104 and the like. Further, “timeout time” can be set via thepanel 309 of the multifunction peripheral, the host computer 101, andthe like. Further, in the logout process, the UI control unit 610notifies the authentication process unit 613 of a logout together withthe user name, the authentication ID, and logout cause information anddiscards authentication information and the authentication ID.

The job management unit 603 analyzes the print job, obtains outputattribute information such as the user name, a number of prints, a colorprint, and the like, and manages the output attribute informationtogether with job start time as job information. When a job such as acopy and the like is issued from the operation panel, the job managementunit 603 receives the output attribute information, the user name, andthe like from the UI control unit 610, and when the job is issued fromthe Web browser, the job management unit 603 receives them from a remoteUI control unit 612. Reference numeral 604 denotes a print datarasterization unit for executing an image generation process byobtaining the print data from the print data storage unit 602 andgenerating image data according to job information stored in the jobmanagement unit 603.

Reference numeral 605 denotes a scanner control unit for controlling thescanner controller 312, scanning a paper document, and generating imagedata. Reference numeral 606 denotes an image storage unit fortemporarily storing the image data generated by the print datarasterization unit 604 and the scanner control unit 605 in the RAM 303and the hard disk (HD) 311.

Reference numeral 607 denotes a printer control unit for controlling aprinter engine 609 and causing it to print image data stored in theimage storage unit 606. The printer engine 609 shows a printer devicefor actually printing image data stored in the image storage unit tomedia such as print papers using a known print technique such as anelectrophotographic technique or an inkjet technique.

Reference numeral 608 denotes a job log management unit for storing andmanaging job log information (job log information illustrated in FIG.7). When a job completed, the job management unit 603 transmits jobinformation to be managed to the job log management unit 608 as the joblog information, and the job log management unit 608 stores the job loginformation. Further, the job log management unit 608 transmits the joblog information in response to a request from the analysis server 104.

The remote UI control unit 612 operates as an HTTP or HTTPS server andreceives a request from the Web browser 404 operating on the hostcomputer 101. When the remote UI control unit 612 receives a requestfrom the Web browser 404, it obtains the authentication information fromsession information and inquires the authentication process unit 613whether access is possible. When the access is permitted by theauthentication process unit 613, the remote UI control unit 612transmits requested HTML data to the Web browser 404. In contrast, whenthe access is not permitted by the authentication process unit 613, theremote UI control unit 612 transmits HTML data for displaying login formscreen to the Web browser 404.

When the remote UI control unit 612 receives input data to a login formfrom the Web browser 404, it transmits an authentication request to theauthentication process unit 613, and when authentication is normallyexecuted, the remote UI control unit 612 transmits the requested HTMLdata to the Web browser 404. The authentication process unit 613executes an authentication process and a management to the multifunctionperipheral. The authentication process unit 613 executes the userauthentication based on a login name, the password, and the like inputby the user to the operation panel 309 and the login name of the Webbrowser 404. Further, the authentication process unit 613 receives theauthentication request from the printer driver 402 and matches the username and the password, and when an authentication is normally executed,it issues the authentication ID and returns the authentication IDtogether with information indicating whether the authentication isnormally executed or fails.

The authentication process unit 613 retains an authenticationinformation table (FIG. 9) and authenticates the user by comparing theuser with the user name and the password registered to the table.Otherwise, the authentication process unit 613 may communicate with aauthentication server (not shown) and may authenticate the user using anauthentication information table retained on the authentication serverside. When the authentication process unit 613 executes theauthentication process, it transmits information such as theauthentication ID, a login user name, login time, logout time, normalauthentication and failed authentication, an authentication route, andthe like as authentication log information and stores the information inan authentication log management unit 611.

Note that information used as authentication route information maydetermine from which module the authentication process unit 613 receivedthe login request, and a module on the login request side may transmitidentification information. Further, when the authentication processunit 613 receives a logout notification, it transmits the received username, authentication ID, and logout cause information to theauthentication log management unit 611, which adds the information tothe authentication log information.

The authentication log management unit 611 stores and managements theauthentication log information (authentication log informationillustrated in FIG. 8 described below). The authentication loginformation includes the authentication ID, the login user name, thelogin time, the logout time, and the like as illustrated in FIG. 8described below. Further, the authentication log management unit 611transmits an authentication log in response to a request from theanalysis server 104.

FIG. 7 is a view illustrating a table (job log information table) forstoring the job log information retained in the job log management unit608. In FIG. 7, reference numeral 701 denotes a job log ID which is anID for uniquely identifying job logs in a system. Reference numeral 702denotes a job type. Shown as the job type 702 here are a print as aprint from the host, a copy and a scan on the multifunction peripheral,a box print for printing documents stored in the multifunctionperipheral. In addition to the above mentioned, SEND for transmittingdata from the multifunction peripheral to an external device, and thelike are also included as the job type.

Reference numeral 703 denotes start time. The job start time can bespecified by the start time 703. Reference numeral 704 denotes end time.A job endpoint can be specified by the end time 704. Reference numeral705 denotes the user name and records the user name of the user whoissued a job. Reference numeral 706 denotes an authentication ID whichis an ID (authentication ID of a login process corresponding to the job)of the authentication log recorded when the job was issued.

The job log management unit 608 records information showing who startswhat job at what time and end it at what time. Reference numerals 711 to713 denote respective job logs. For example, reference numeral 711 showsa job log as to a “print” job which was started by a user “Matsuki” at“2007/04/30 14:31:33” and ended at “2007/04/30 14:34:36”. Note that thejob log information table may be arranged to each type of job.

FIG. 8 is a view illustrating a table (authentication log informationtable) for storing the authentication log information retained in theauthentication log management unit 611. In FIG. 8, reference numeral 801denotes an log ID which is an ID for uniquely identifying theauthentication logs in the system. Reference numeral 802 denotes anauthentication ID which is issued by the authentication process unit 613when an authentication is normally executed. Here, the authentication isnormally executed and the user normally executes the login process.Reference numeral 803 denotes a user name designated when theauthentication request is issued. Reference numeral 804 denotes time atwhich the authentication (login) request is issued. When anauthentication is normally executed, the time has the same meaning asthe login time. Accordingly, the login time can be specified by theauthentication time 804 at which the authentication request is issued.Reference numeral 805 denotes the logout time which records time atwhich the user designates a logout by the operation panel 309 and theWeb browser 404, and time at which the logout is automatically executedwhen an operation is not executed for a predetermined time. The logoutpoint can be specified by the logout time 805.

Reference numeral 806 denotes a logout cause which records whether theuser designates the logout by the operation panel 309 and the Webbrowser 404 (user manipulation) and whether the logout is automaticallyexecuted when the operation is not executed for the predetermined time(timeout). Reference numeral 807 denotes an authentication route forrecording a type of a module which transmits the authentication requestto the authentication process unit 613. Exemplified as a type of theauthentication route are the operation panel 309 (panel) the Web browser404 (Web), the printer driver 402 (driver), and the like. Referencenumeral 808 denotes a result and records whether an authentication isnormally executed or fails.

Reference numerals 811 to 815 denote respective authentication logs. Theauthentication log 811 shows that the user “Matsuki” normally executed alogin from “panel” at “2007/04/30 14:35:30” and executed a logout by“user manipulation” at “2007/04/30 14:30:30”.

FIG. 9 is a table for storing authentication information of respectiveusers retained by the authentication process unit 613. In FIG. 9,respective rows show user entries, and respective columns describe theauthentication information of the respective users. Reference numeral1201 denotes the user name, and reference numeral 1202 denotes thepassword. The row 1211 shows a user entry of name “Kato”. The passwordhas a character string of “Akd5sj4f”. Likewise, a user entry of name“Matsuki” is defined in row 1212, and a user entry of name “Sakai” isdefined in row 1213.

FIG. 10 is a flowchart illustrating an analysis flow for an in-operationtime executed by the analysis server 104 according to the firstexemplary embodiment of the invention. The process illustrated in theflowchart is executed by respective functional units of the analysisserver 104. That is, the process is realized by the CPU 201 of theanalysis server 104, which reads and executes a program stored on the HD211 and the like of the analysis server 104.

First, in step S1501, the analysis processing unit 502 of the analysisserver 104 starts a job processing time analysis process. In step S1502,the job log collection unit 503 of the analysis server 104 communicateswith the multifunction peripherals 102 and 103 via the I/F unit 501 andcollects the job log information managed by the job log management unit608. Then, the job log collection unit 503 stores the obtained job loginformation in a job log information table as illustrated in FIG. 7.Note that the job log information is stored in a table of the type inwhich columns (not illustrated) of “corrected in-operation time” aredisposed to the job log information table in FIG. 7. Further, when thelog information is collected from plural devices, it is managed bycolumns of device identifiers disposed on the table.

Subsequently, in step S1503, the authentication log collection unit 504of the analysis server 104 communicates with the multifunctionperipherals 102 and 103 via the I/F unit 501 and collects theauthentication logs managed by the authentication log management unit611. Then, the authentication log collection unit 504 stores theobtained authentication logs with the authentication log informationtable as illustrated in FIG. 8. Note that the obtained authenticationlogs are stored in a table of the type in which columns of “correctedin-operation time” (not illustrated) are disposed to the authenticationlog information table in FIG. 8. Further, when the log information iscollected from plural devices, it is managed by columns of deviceidentifiers disposed on the table.

Processes for calculating the in-operation time will be described below.In a loop of steps S1504 to S1506, the analysis processing unit 502executes control for sequentially processing the respectiveauthentication logs obtained in step S1503 as processing targets andexecuting a process in step S1505. In step S1505, the analysisprocessing unit 502 executes a calculation process of the in-operationtime by the authentication logs as the processing targets. That is, theanalysis processing unit 502 calculates in-operation times due to loginscorresponding the authentication logs as the processing targets(including in-operation times corresponding to in-operation timescorresponding to predetermined operations and in-operation timescorresponding to job processing times). The in-operation timecalculation process will be described in detail in FIG. 13 to bedescribed below.

Then, when the analysis processing unit 502 executes the process in stepS1505 to all of the authentication logs, it exits the loop of stepsS1504 to S1506 and goes to step S1507. In step S1507, the analysisprocessing unit 502 totals the in-operation times calculated in stepsS1504 to S1506, calculates total in-operation times of respectivedevices, and outputs them to an analysis result table (FIG. 14). Then,the analysis process of the job processing time is ended (step S1508).Note that the in-operation time addition process in step S1507 will bedescribed below in detail in FIG. 15.

The calculation process of the in-operation time in step S1505 in FIG.10 will be described below in detail referring to FIGS. 11 to 13. FIG.11 is a view illustrating a concept of the in-operation time calculationprocess relating to a job process in the analysis processing unit 502 ofthe analysis server 104.

<Simple system> In FIG. 11, the vertical axis shows a time axis, and aright direction shows a flow of time. In FIG. 11, an authentication log811 corresponds to the authentication log 811 of the authentication loginformation table in FIG. 8. The authentication log 811 shows that alogin was executed at “2007/04/30 14:30:30” and a logout was executed at“2007/04/30 14:35:30”. In contrast, a job log 711 corresponds to the joblog 711 of the job log information table in FIG. 7. The job log 711shows that a job was started at “14:31:33” and ended at “14:34:36”.

An in-operation time of a job (pure job processing time) when anin-manipulation time until the job is issued in a device is not takeninto consideration is determined by the following expression:In-operation time of job when in-manipulation time is not taken intoconsideration=[job end time]−[job start time]

Since a copy job of the job log 711 has an authentication ID “010”, itcan be found that a job was issued during login periods 1002 to 1003illustrated in the authentication log 811 whose authentication ID agreeswith the authentication ID “010”. Therefore, a manipulation is startedfrom time 1012 in which the user logs in, and the job is started at time1012 and ended at time 1013. That is, it is presumed that a period fromtime 1002 to time 1012 is an in-manipulation time, and a period fromtime 1012 to time 1013 becomes a job processing time.

From what has been described above, it is considered that thein-operation time of the device due to the job illustrated by the joblog 711 is time 1002 to time 1013, that is, a time illustrated by 1020in FIG. 11. Further, when plural jobs are processed based on a loginexecuted once, it is presumed that a time from end time of a most recentjob to start time of each of the jobs processed second and thereafter isa manipulation time thereof. From what has been described above, it isconsidered that an in-operation time of a device due to the job is atime from the end time of the most recent job to the start times thejobs (in-manipulation time of the user)+the time from the end time ofthe job to the start times of the job (job processing time). That is, itis considered that the in-operation time of the device due to the job isfrom the end time of the most recent job to the end time of the job.

As illustrated in the above, it is considered that a time until a firstjob starts after the user logs in. Therefore, these times (the userin-manipulation times) are added to the job processing time, and thein-operation time is corrected (hereinafter, called a correctedin-operation time). As a result, an in-operation time nearer to anactual in-operation time cab be determined. Note that, since a logoutcause of the authentication log 811 is “user manipulation” and theauthentication route 807 is “panel”, it can be found that a copy jobends at time 1013, and a logout is executed at time 1003 by the usermanipulating the panel. That is, it is presumed that a period from time1013 to time 1003 is a logout in-manipulation time by the user.

From what has been described above, it is considered that the userin-manipulation time due to the authentication log 811 is the periodfrom time 1002 to time 1012 and the period from time 1013 to time 1003.That is, it is considered that a user in-manipulation period due to theauthentication log 811 is a period which does not overlap the jobprocessing periods 1012 to 1013 of the relating job log 711 of the loginperiods 1002 to 1003 of the authentication log 811. Note that this isthe same as a case where plural jobs are processed based on a loginexecuted once. However, when the logout cause is “timeout”, and thelike, it is necessary to remove a period required for the timeout fromthe user in-manipulation period (this will be described in detail in thefollowing “without-job system”).

<Without-job system> When the user manipulates the device, he or shedoes not necessarily issue a job. There may be a case where the userexecutes a manipulation for browsing, editing, deleting, and the like ofa document registered to the multifunction peripheral, and there is alsoconsidered a case where the user ends a manipulation when it is beingexecuted without issuing a job. Since the device is occupied during thetime (in-manipulation time), the time must be included in thein-operation time. FIG. 12 is a view illustrating a concept of acalculation process of the in-operation time by an authentication log inthe analysis processing unit 502 of the analysis server 104. In FIG. 12,the vertical axis indicates a time axis and a right direction shows aflow of time. In FIG. 12, an authentication log 814 corresponds to theauthentication log 814 of the authentication log information table inFIG. 8. The authentication log 814 shows that a login was executed at“2007/05/01 10:01:00” and a logout was executed at “2007/05/0110:10:00”.

Further, in the authentication log 814, the logout cause is the“timeout”. In this case, the user naturally executes no manipulation ina time during which a timeout occurs before a logged-out time (period1111 in FIG. 12). Further, the user can ordinarily use the device duringthe above time. The period 1111 in FIG. 12, during which no job isprocessed and the user executes no manipulation at all, must not beincluded in the in-operation time. Therefore, in this case, a time 1110,from which the timeout time 111 in FIG. 12 is omitted becomes thein-operation time by the authentication log 814. In the example in FIG.12, login time up to time at which a logout 1102 is executed after alogin 1101 is 9 minutes (10:01 to 10:10), and when, for example, thetimeout time (1111) is 3 minutes, the in-operation time is 6 minutes.Here, it is regarded that a time at which the user ends the manipulationis time 1103.

Note that setting of the timeout time is retained by the UI control unit610 of the multifunction peripheral and can be obtained also from theanalysis server 104 via the network. In contrast, when the logout causein the authentication log 814 is the “user manipulation”, since it isconsidered that the user occupies the device also in a time until thelogout is executed after a job ends (in-manipulation time), the timemust be included in the in-operation time. That is, it is consideredthat a user in-manipulation period due to the authentication log 814 isa period which does not overlap the job processing period of therelating job log of the login period from time 1101 to time 1102 of theauthentication log 814. Note that when a relating job is not issued, thelogin period agrees with the user in-manipulation period.

Accordingly, in any of the <simple system> and the <without-job system>,a device in-operation time is shown as follows. In the job processingperiod (first in-operation period) and a period in which the user logsin, a sum of times corresponding to a user in-manipulation period(second in-operation period) becomes an in-operation time of the device.However, when the logout cause is the “timeout”, a period necessary tothe timeout is not included in the user in-manipulation period.

Further, although a detail will be described below, when theauthentication route 807 is “Web”, the multifunction peripheral is notoccupied and a process is not executed in a time from a job end to alogout. Therefore, when the authentication route 807 is “Web”, it is notnecessary to include a period from time at which a final relating jobends to time of the logout in the in-operation time. Accordingly, whenthe authentication route 807 is “Web”, the period from the time at whichthe final relating job ends to the time of the logout in thein-operation time is not included in the user in-manipulation period.Further, when the authentication route 807 is a “driver”, a time otherthan the job processing time is not occupied by the multifunctionperipheral, it is not necessary to include the time other than the jobprocessing time to the in-operation time. Accordingly, when theauthentication route 807 is “driver”, the login period of the driver isnot included in the user in-manipulation period.

FIG. 13 is a flowchart illustrating an example of a detailed flow in thein-operation time calculation process (calculation process of thein-operation time including a correction process by each authenticationlog) illustrated in step S1505 in FIG. 10. The process illustrated inthe flowchart is executed by the analysis processing unit 502 of theanalysis server 104. That is, the process is realized by the CPU 201 ofthe analysis server 104, which reads and executes a program stored inthe HD 211 and the like of the analysis server 104.

First, in step S901, the analysis processing unit 502 of the analysisserver 104 starts the in-operation time calculation process to anauthentication log of a processing target. In step S902, the analysisprocessing unit 502 determines whether an authentication route 807 ofthe authentication log of the processing targets is the “driver”(printer driver). When the analysis processing unit 502 determines thatthe authentication route 807 is the “driver”, the analysis processingunit 502 ends the in-operation time calculation process (steps S923).Note that the authentication processing executed from the printer driver402, after the authentication processing from the printer driver 402ends, a print job is input to the multifunction peripheral via thenetwork 105. Therefore, the multifunction peripheral is not occupied ina time until the job is input and no process is executed. Therefore, inthis case, a time from a login to a start of the job, a time from an endof a most recent job to a start of a next job, and a time from an end ofa final job to a logout are not included to the in-operation time.

Note that although the process is ended in step S902 when theauthentication route 807 is the “driver”, the process may be ended whenthe authentication route 807 is the “driver” or the “Web” (that is, whenit is not the “panel”). In contrast, when it is determined step S902that the authentication route 807 is not the “driver”, the analysisprocessing unit 502 goes to a process in step S925. In step S925, theanalysis processing unit 502 determines whether the result 808 of theauthentication log of the processing target is “failed”. When theanalysis processing unit 502 determines that the result 808 is “failed”,the analysis processing unit 502 ends the in-operation time calculationprocess (steps S923). In the exemplary embodiment, when the loginprocess fails, a login process time is not included in the in-operationtime, it may be included in the in-operation time.

In contrast, when it is determined in step S925 that the result is not“failed”, the analysis processing unit 502 goes to a process in stepS903. In step S903, the analysis processing unit 502 refers to a job logtable retained by the job log collection unit 503 and searches job logsin which the authentication log 706 agrees with an attribute of theauthentication ID 802 of the authentication log of the processingtarget. Further, the analysis processing unit 502 sorts the searched joblogs in an ascending order of the start times 703.

Subsequently, in step S904, the analysis processing unit 502 initializesvariables As, Ae, and Ao stored in the RAM 203 of the analysis server104 by the following values.

-   As=login time (authentication (login) date and time 804 of    authentication log of processing target)-   Ae=logout time (logout time 805 of authentication log of processing    target)-   Ao=timeout time    Note that the timeout time is retained by the UI control unit 610 of    the multifunction peripheral of an acquisition source of the    authentication log and obtained via the network. The analysis    processing unit 502 may previously obtain the timeout times of the    respective multifunction peripherals.

Subsequently, in a loop of steps S905 to S916, the analysis processingunit 502 executes control for sequentially processing the job logssearched in step S903 as processing targets and executing processes instep S906 to step S915. Note that when no job log is searched in stepS903, the analysis processing unit 502 exits the loop of steps S905 toS916 as it is and goes to a process in step S917.

First, in step S906, the analysis processing unit 502 evaluates anexpression “As<Ae”, and when the analysis processing unit 502 determinesthat the expression “As<Ae” is true, it goes to a process in step S907.In step S907, the analysis processing unit 502 initializes variables Js,Je, and Jw stored in the RAM 203 of the analysis server 104 as describedbelow.

-   Js=start time (start time 703 of job log of processing target)-   Je=end time (end time 704 of job log of processing target)-   Jw=0    Subsequently, in step S908, the analysis processing unit 502    evaluates an expression “Ae<Js”, and when the analysis processing    unit 502 determines that the expression “Ae<Js” is false, it goes to    a process in step S924.

In step S924, the analysis processing unit 502 evaluates the expression“As<Js”, and when analysis processing unit 502 determines that theexpression “As<Js” is true, it goes to a process in step S909. Notethat, when the expression “As<Js” is true, it is shown that a time froma login to a logout overlaps a time from a start of a job to an end ofthe job. In step S909, the analysis processing unit 502 substitutes avalue for the variable Jw showing a corrected in-operation time as shownby “Jw=Je−As”. This is a time corresponding to the period 1020 in theconceptual view in FIG. 11. That is, the corrected operating time is atime corrected by adding the in-manipulation time “Js−As” to the jobprocessing time “Je−Js” as conventional in-operation times. Accordingly,the corrected in-operation time may be shown as “Jw=Je−Js+Js−As”.

Next, in step S910, the analysis processing unit 502 updates thevariable As by the value Je. This is a step for changing the time, whichcan be used as the corrected in-operation time, Je to Ae because thetime As to Je of the time As to Ae, which can be used as the correctedin-operation time, is already used as the corrected in-operation time instep S909. With this operation, A job end time of the processing targetis stored as the variable As.

When the process in step S910 ends, the analysis processing unit 502goes to a process in step S915. In contrast, when it is determined instep S924 that the expression “As<Js” is false, the analysis processingunit 502 goes to a process in step S916, and when a job log which is notyet processed remains, the analysis processing unit 502 shifts theprocessing target to a next job log. Note that a reason why theexpression “As<Js” may become false resides in that plural jobs areexecuted in parallel and As is changed to end time of another job inplace of login time by the process in step S910 to another job log. Inthis case, the processing target is shifted to a next job log withoutparticularly executing a process thereto to avoid that a correctedin-operation time is calculated by adding an in-manipulation time twice.

In contrast, when it is determined in step S908 that the expression“Ae<Js” is true, the analysis processing unit 502 goes to a process instep S911. Note that when the expression “Ae<Js” is true, this showsthat a job starts after a logout. In step S911, the analysis processingunit 502 determines whether the logout cause 806 of an authenticationlog of the processing target is “timeout”, and when the analysisprocessing unit 502 determines that it is not “timeout”, the analysisprocessing unit 502 goes to a process in step S912.

In step S912, the analysis processing unit 502 calculates the correctedin-operation time Jw by the following calculating formula.Jw=(Je−Js)+(Ae−As)This shows that the corrected in-operation time Jw when a job startsafter a logout which is not a timeout is a time obtained by adding thejob processing time “Je−Js” to the time “Ae−As” from a login to alogout. In this case, the time “Ae−As” from the login to the logoutbecomes an in-manipulation time. Accordingly, corrected in-operationtime Jw=job processing time “Je−Js”+in-manipulation time “Ae−As” isestablished. When the process in step S912 ends, the analysis processingunit 502 goes to a process in step S914.

In contrast, when it is determined in step S911 that the logout cause806 of the authentication log of the processing target is the “timeout”,the analysis processing unit 502 goes to a process in step S913. In stepS913, the corrected in-operation time Jw is calculated by the followingcalculating formula.Jw=(Je−Js)+(Ae−As−Ao)This means that the corrected in-operation time Jw by a job log of ajob, which starts after a logout due to a timeout, is a time obtained byadding a time, which is obtained by subtracting a timeout time Ao fromthe time “Ae−As” from the login to the logout, to the job processingtime “Je−Js”. Note that the time “Ae−As−Ao” is a time corresponding tothe period 1110 in the conceptual view in FIG. 12. In this case, thetime “Ae−As−Ao”, which is obtained by subtracting the timeout time Aofrom a time from the login to the logout, becomes the in-manipulationtime. Accordingly, corrected in-operation time Jw=job processing time“Je−Js”+in-manipulation time “Ae−As−Ao” is established.

When the process in step S913 ends, the analysis processing unit 502goes to a process in step S914. Next, in step S914, the analysisprocessing unit 502 updates the variable As by Ae. This shows that atime, which can be used as the corrected in-operation time, does notremain because the time from the login to the logout is already used asthe corrected in-operation time in step S912 or S913. When the processin step S914 ends, the analysis processing unit 502 goes to a process instep S915.

Next, in step S915, the analysis processing unit 502 sets a value of thevariable Jw calculated in step S910, S912, or S913 to a column (notshown) of the “corrected in-operation time” of a job log table of thelog job. When the process in step S915 ends, the analysis processingunit 502 goes to a process in step S916, and when a non-processed joblog still remains, the analysis processing unit 502 shifts theprocessing target to a next job log. In contrast, when it is determinedin step S906 that the expression “As<Ae” is false, the analysisprocessing unit 502 goes to a process in step S916, and when thenon-processed job log still remains, the analysis processing unit 502shifts the processing target to the next job log. Note that, when theexpression “As<Ae” is false, this means that although the time As to Aeis a time which can be added to the in-operation time, since thevariable As is updated by the processes in step S910 or S914, a time,which can be used as the corrected in-operation time, does not remain.

When loop processes in steps S905 to S916 end and a correction processto all of the job logs (all of the job logs searched in step S903)relating to the authentication log of the processing target ends, theanalysis processing unit 502 goes to a process in step S917. In stepS917, the analysis processing unit 502 evaluates the expression “As<Ae”,and when the analysis processing unit 502 determines that the expression“As<Ae” is false, it goes to step S923 and ends the process. This meansthat a time which can be added as the in-operation time does not remain.

In contrast, when it is determined in step S917 that the expression“As<Ae” is true, the analysis processing unit 502 goes to a process instep S918. In step S918, the analysis processing unit 502 determineswhether the attribute of the authentication route 807 of theauthentication log of the processing target is the “panel”, and when theanalysis processing unit 502 determines that it is not the “panel”, theanalysis processing unit 502 goes to step S923 and ends the process.This case includes a case where the authentication route is the “Web”.When the authentication route is the “Web”, a time in which the useronly accesses a browser is not included in the in-operation time, andonly when a job is issued, an in-manipulation time for issuing the jobis included in the in-operation time.

In contrast, when it is determined in step S918 that the attribute ofthe authentication route 807 of the authentication log of the processingtarget is the “panel”, the analysis processing unit 502 goes to aprocess in step S919. The analysis processing unit 502 determines instep S919 whether the logout cause 806 of the authentication log of theprocessing target gets the “timeout”, and the analysis processing unit502 determines that the logout cause 806 does not get the “timeout”, itgoes to a process in step S920. In step S920, the analysis processingunit 502 calculates a corrected in-operation time Aw of theauthentication log by the following calculating formula.Aw=Ae−AsThis shows that the corrected in-operation time Aw of the authenticationlog, which does not get the “timeout”, becomes the time “Ae−As”(in-manipulation time) from the login to the logout.

When the process in step S920 ends, the analysis processing unit 502goes to a process in step S922. In contrast, when it is determined instep S919 that the logout cause 806 of the authentication log gets the“timeout”, the analysis processing unit 502 goes to a process in stepS921. In step S921, the analysis processing unit 502 calculates thecorrected in-operation time Aw of the authentication log by thefollowing calculating formula.Aw=Ae−As−AoThis shows that the corrected in-operation time Aw of the authenticationlog which gets the “timeout” becomes a time (in-manipulation time)obtained by subtracting the timeout time Ao from the time “Ae−As” fromthe login to the logout. This is a time corresponding to the period 1110in the conceptual view in FIG. 12.

When the process in step S921 ends, the analysis processing unit 502goes to a process in step S922. Note that “As” used in steps S920 orS921 may be changed from the authentication (login) date and time 804 asan initial value in steps before the above steps. This is a case where“As” is already used for correction and addition in the in-operationtime processes (steps S905 to S916) of the job log. In this case, “As”is set to end time and the like of a final job. For example, in stepS920, a time from the end time 1013 in the row 711 in FIG. 11 to thelogout time 1003 in the row 811 is used for the corrected in-operationtime Aw as an in-manipulation time.

Subsequently, in step S922, the analysis processing unit 502 sets Awcalculated in step S920 or S921 to a column (not illustrated) of the“corrected in-operation time” of the authentication log of theauthentication log table and ends the in-operation time calculationprocess (steps S923).

Next, an in-operation time addition process in step S1507 in FIG. 10will be described in detail referring to FIGS. 14 to 15. The analysisresult table in which an analysis result (in-operation time additionresult) is output in step S1507 in FIG. 10 will be described. FIG. 14 isa view illustrating a configuration of the analysis result table. Notethat the analysis result table is stored in the storage device 211. InFIG. 14, reference numeral 1401 denotes a multifunction peripheral ID towhich an ID for identifying the multifunction peripheral is set.Reference numeral 1402 denotes an in-operation time in which anin-operation time calculated by the in-operation time addition processin step S1507 in FIG. 10 is stored.

FIG. 15 is a flowchart illustrating an example of a detailed flow of thein-operation time addition process illustrated in step S1507 in FIG. 10.The process illustrated in the flowchart is executed by the analysisprocessing unit 502 of the analysis server 104. That is, the process isrealized by the CPU 201 of the analysis server 104, which reads andexecutes a program stored in the HD 211 and the like of the analysisserver 104.

First, in step S1301, the analysis processing unit 502 starts thein-operation time addition process. Next, in a loop of steps S1302 toS1316, the analysis processing unit 502 executes control forsequentially processing the respective multifunction peripherals managedby the analysis server 104 as processing targets and executing processesin step S1303 to S1315.

First, in step S1303, the analysis processing unit 502 initializes thevariable Dw, which shows the in-operation time of the multifunctionperipheral of the processing target stored in the RAM 203 of theanalysis server 104, by “0”. Subsequently, in step S1304, the analysisprocessing unit 502 searches a job log of the multifunction peripheralof the processing target by a job log table retained by the job logcollection unit 503. Next, in a loop of steps S1305 to S1309, theanalysis processing unit 502 executes control for sequentiallyprocessing all of the job logs searched in step S1304 as processingtargets and executing processes in steps S1306 to S1318.

First, in step S1306, the analysis processing unit 502 determineswhether the “corrected in-operation time” of a job log of the processingtarget is set, and when the analysis processing unit 502 determines thatthe “corrected in-operation time” is set, it goes to a process in stepS1307. In step S1307, the analysis processing unit 502 adds the“corrected in-operation time” of the job log to a variable Dw. Notethat, as illustrated in the flowchart in FIG. 13, the “correctedin-operation time” of the job log means job in-operation time+processingtime.

In contrast, when the analysis processing unit 502 determines in stepS1306 that the “corrected in-operation time” of the job log of theprocessing target is not set, it goes to a process in step S1308. Instep S1308, the analysis processing unit 502 adds a time, which isobtained by subtracting the start time 703 from the end time 704 of thejob log of the processing target, to the variable Dw. This means thatwhen the in-operation time is not corrected by the authentication log,the processing time of a job is added as the in-operation time. When theprocess in step S1307 or S1308 ends, the analysis processing unit 502goes to a process in step S1309, and when a non-processed job log stillremains, it shifts the processing target to a next job log.

In contrast, when the analysis processing unit 502 determines in stepS1309 that all of the job logs searched in step S1304 have beenprocessed in step S1306 to S1308, it exits a loop of steps S1305 toS1309 and goes to a process in step S1310. In step S1310, the analysisprocessing unit 502 searches the authentication log of the multifunctionperipheral of the processing target by the authentication log tableretained by the authentication log collection unit 504. Next, in a loopof steps S1311 to S1314, the analysis processing unit 502 executescontrol for sequentially processing all of the authentication logssearched at the S1310 as processing targets and executing processes insteps S1312 to S1313.

First, in step S1312, the analysis processing unit 502 determineswhether the “corrected in-operation time” of the authentication log ofthe processing target is set, and when the “corrected in-operation time”is set, the analysis processing unit 502 goes to a process in stepS1313. In step S1313, the analysis processing unit 502 adds the“corrected in-operation time” of the authentication log to the variableDw and goes to a process in step S1314. In contrast, in step S1312, whenthe analysis processing unit 502 determines that the “correctedin-operation time” of the authentication log of the processing target isnot set, it goes to a process in step S1314 as it is.

When a non-processed authentication log still exists, the analysisprocessing unit 502 shifts the processing target to a nextauthentication log step in step S1314. In contrast, when the analysisprocessing unit 502 determines in step S1314 that all of the job logssearched in step S1310 have been processed in step S1312 to S1313, itexits a loop of steps S1311 to S1314 and goes to a process in stepS1315.

Next, in step S1315, the analysis processing unit 502 adds a row to anin-operation time analysis result table illustrated in FIG. 14, sets anidentifier of the multifunction peripheral of the processing target tothe multifunction peripheral ID 1401, and sets Dw to the in-operationtime 1402. When a non-processed multifunction peripheral remains in stepS1316, the analysis processing unit 502 shifts the processing target toa next multifunction peripheral. In contrast, when the analysisprocessing unit 502 determines in step S1316 that all of themultifunction peripherals have been processed in step S1303 to S1315,the analysis processing unit 502 exits a loop of steps S1302 to S1316and ends the processes (steps S1317).

As described above, since the in-operation time of the device iscalculated by adding the user in-manipulation time by the authenticationlog (specified by the authentication log and the authentication log) tothe job processing time by the job log, the in-operation time of thedevice nearer to an actual in-operation time can be calculated. Notethat, in steps S909, S912, and S913 in FIG. 13, the value, which isobtained by adding the user in-manipulation time to the job processingtime, is calculated as the corrected in-operation time by the job log.However, in steps S909, S912, and S913 in FIG. 13, the userin-manipulation time may be calculated as an “in-manipulation time” by ajob log. In this configuration, step S1307 in FIG. 15 is set toDW=DW+“in-operation time”+(job end time−job start time). With thisconfiguration, a result similar to the exemplary embodiment describedabove can be obtained.

In the first exemplary embodiment, since the authentication ID of thejob log of the multifunction peripheral is set, a relation between theauthentication log and the job log is apparent. In a second theexemplary embodiment of the invention, a method for relating a job logto an authentication log when an authentication ID is not set to a joblog of a multifunction peripheral will be described. That is, in a joblog information table according to the present exemplary embodiment, itis assumed that a column of an authentication ID 706 is not set.

FIG. 16 is a flowchart illustrating a flow by the analysis server 104 inthe second exemplary embodiment. A process illustrated in the flowchartis executed by respective functional units of the analysis server 104.That is, the process is realized by the CPU 201 of the analysis server104, which reads and executes a program stored in the HD 211 and thelike of the analysis server 104. Note that an analysis process of anin-operation time in the present exemplary embodiment is executed byadding step S1509 between step S1503 and step S1504 of the analysisprocess of the in-operation time illustrated in FIG. 10 in the first theexemplary embodiment described above.

In step S1509 in FIG. 16, the analysis process unit 502 executes anauthentication ID setting process (FIG. 18) for setting anauthentication ID to a job log. The authentication ID setting process instep S1509 will be described below referring to FIGS. 17 and 18. First,an authentication route/job type relating table retained by an analysisprocess unit 502 of the analysis server 104 will be described using FIG.17. FIG. 17 is a view illustrating the authentication route/job typerelating table retained by the analysis process unit 502 of the analysisserver 104. As illustrated in FIG. 17, the authentication route/job typerelating table shows an authentication route 1701 and a job type 1702capable of being related to an authentication log of the authenticationroute.

A record of the row 1711 shows that an authentication log whoseauthentication route is “panel” (operation panel) can be related to ajob log whose job type is “copy”, “box print”, and “scan”. Likewise, arecord of the row 1712 shows that an authentication log whoseauthentication route is “Web” (Web browser) can be related to a job logwhose job type is “box print”. Likewise, a record of the row 1713 showsthat an authentication log whose authentication route is “driver” can berelated to a job log whose job type is “print”.

A job type to be issued changes depending on by which module the userexecutes a manipulation. Therefore, the table is used to prevent anon-relational authentication log from being related to a job log bymistake. Note that the authentication route/job type relating table canbe fixed to a system or can be set by the user.

Next, a flow of a detailed process of job log authentication ID settingstep S1509, which is processed by the analysis process unit 502, will bedescribed using a flowchart illustrated in FIG. 18. The process shown inthe flowchart is executed by the analysis process unit 502 of theanalysis server 104. That is, the process is realized by the CPU 201 ofthe analysis server 104, which reads and executes a program stored inthe HD 211 and the like of the analysis server 104. First, in stepS1601, the analysis process unit 502 starts the authentication IDsetting process. In a loop of step S1602 to S1608, the analysis processunit 502 executes control for sequentially processes job logs collectedby the job log collection unit 503 as processing targets and executingprocesses in steps S1603 to S1607.

First, in step S1603, the analysis processing unit 502 searches anauthentication log in which a user name 705 of a job log of a processingtarget agrees with a login user name (user name 803). Subsequently, instep S1604, the analysis process unit 502 refers to the authenticationroute/job type relating table in FIG. 17, searches a row in which a jobtype 702 of a job log of the processing target is included in a columnof the job type 1702, and obtains the authentication route 1701 in therow. When, for example, the job type is “box print”, rows 1711 and 1712,in which “box print” is included in the column of the job type 1702, aresearched, and “panel” and “Web” which are the authentication route 1701in the row are obtained. Subsequently, in step S1605, the analysisprocess unit 502 searches an authentication log, in which anauthentication route 807 of the authentication log is included in theauthentication route obtained in step S1604 in the authentication logssearched in step S1603.

Next, in step S1606, the analysis process unit 502 selects anauthentication log which is a nearest authentication (login) time 804before start time 703 of a job log in the authentication logs searchedin step S1605. Next, in step S1607, the analysis process unit 502 setsan authentication ID of an authentication log selected in step S1606 tothe column of the authentication ID 706 of the job log of a job logtable retained by the job log collection unit 503 and relates the joblog to the authentication log. That is, the authentication ID of theauthentication log selected in step S160 is set to an authentication ID706 of the job log of the processing target in the job log table, andthe job log is related to the authentication log.

In step S1608, the analysis process unit 502 determines whether theprocesses in steps S1603 to S1607 have been ended to all of the joblogs, and when they have not been yet ended, the analysis process unit502 shifts the processing target to a next job. In contrast, when theanalysis process unit 502 determines that the processes in steps S1603to S1607 have been ended to all of the job logs, it exits a loop ofsteps S1602 to S1608 and ends the authentication ID setting process(step S1609).

Thereafter, the analysis process unit 502 analyzes a job processing timeby executing the processes in step S1504 and subsequent steps in FIG. 16using the job logs related as described above and the authenticationlog. As described above, even if a relation of the authentication log tothe job log is not apparent, an in-operation time of a device nearer toa time in which the device is actually used can be calculated byrelating the authentication log to the job log from the relation of theuser name, the login time, and processing time.

Note that it is needless to say that the configurations and the contentsof the various types of data described above are not limited thereto andcan be arranged by various configurations and contents depending on ause and an object. A described above, although an exemplary embodimenthas been shown, the invention can employ an embodying mode as, forexample, a system, an apparatus, a method, a program, a storage medium(recording medium), and the like. Specifically, the invention may beapplied to a system composed of a plurality of devices and furtherapplied to an apparatus composed of a single device.

In the calculation of an in-operation time of a device, a time in whichthe device is used must be measured. However, since a conventionalmethod calculates the in-operation time of the device only by a jobprocessing time, the method is insufficient. The exemplary embodimentcan calculate an in-operation time of a device nearer to a time in whichthe device is actually used by correcting an in-operation time of thedevice using the authentication log and presuming a time from a start ofa manipulation of a user to a completion of a job.

Aspects of the present invention can also be realized by a computer of asystem or apparatus (or devices such as a CPU or MPU) that reads out andexecutes a program recorded on a memory device to perform the functionsof the above-described embodiment (s), and by a method, the steps ofwhich are performed by a computer of a system or apparatus by, forexample, reading out and executing a program recorded on a memory deviceto perform the functions of the above-described embodiment (s). For thispurpose, the program is provided to the computer for example via anetwork or from a recording medium of various types serving as thememory device (e.g., computer-readable medium).

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all modifications, equivalent structures, and functions.

This application claims priority from Japanese Patent Application No.2009-060640 filed Mar. 13, 2009, which is hereby incorporated byreference herein in its entirety.

What is claimed is:
 1. An information processing apparatus configured tocalculate an in-operation time of an image processing apparatus, theinformation processing apparatus comprising: an authentication logacquisition unit configured to acquire an authentication log includinginformation capable of specifying login time and logout time of a loginprocess in the image processing apparatus; a job log acquisition unitconfigured to acquire a job log including information capable ofspecifying job start time and job end time of a job processed by theimage processing apparatus; and a calculation unit configured tocalculate the in-operation time of the image processing apparatus basedon a first in-operation period corresponding to a job processing periodspecified by the job log and a second in-operation period correspondingto a period other than a job processing period specified from a job logrelating to the authentication log, in a login period specified from theauthentication log, wherein the second in-operation period correspondsto an in-manipulation time during which the user inputs to the imageprocessing apparatus, and wherein, as to a login period specified by anauthentication log whose logout cause is specified to be timeout, thecalculation unit does not include a period necessary to the timeout intothe second in-operation period.
 2. The information processing apparatusaccording to claim 1, wherein the authentication log includesinformation for specifying whether a corresponding login process isexecuted by a user manipulation via a network; and wherein, as to alogin period specified from an authentication log whose login process isspecified to be executed by a user manipulation via a network, thecalculation unit does not include, in the second in-operation period, aperiod from end time to logout time of a latest job processing period ina job processing period of a job log relating to the authentication log.3. The information processing apparatus according to claim 1, whereinthe authentication log includes information for specifying whether acorresponding login process is executed by a printer driver; and whereinthe calculation unit does not include, in the second in-operationperiod, a login period specified from an authentication log whose loginprocess is specified to be executed by a printer driver.
 4. Theinformation processing apparatus according to claim 1, wherein theauthentication log includes a user name when a corresponding loginprocess is executed; wherein the job log includes a user name who issuesa corresponding job; and wherein the calculation unit specifies a joblog relating to the authentication log by the user name.
 5. Theinformation processing apparatus according to claim 4, wherein thecalculation unit specifies a job log whose job start time is later thanlogin time of the authentication log and is nearest to the login time asjob log information relating to the authentication log.
 6. Theinformation processing apparatus according to claim 1, wherein theauthentication log includes information for specifying an authenticationroute of a corresponding login process; wherein the job log includesinformation for specifying a job type of a corresponding job; andwherein the calculation unit specifies that the authentication log andthe job log relate to each other when a combination of the job typeincluded in the job log and the authentication route included in theauthentication log agrees with a previously set combination of a jobtype and an authentication route.
 7. The information processingapparatus according to claim 1, wherein the authentication log includesan authentication ID issued when a corresponding login process isexecuted; wherein the job log includes an authentication IDcorresponding to a login process when a corresponding job is processed;and wherein the calculation unit specifies a job log relating to theauthentication log by the authentication ID.
 8. A method for calculatingan in-operation time of an image processing apparatus, the methodcomprising the steps of: acquiring an authentication log includinginformation capable of specifying login time and logout time of a loginprocess in the image processing apparatus; acquiring a job log includinginformation capable of specifying job start time and job end time of ajob processed by the image processing apparatus; and calculating thein-operation time of the image processing apparatus based on a firstin-operation period corresponding to a job processing period specifiedby the job log and a second in-operation period corresponding to aperiod other than a job processing period specified from a job logrelating to the authentication log, in a login period specified from theauthentication log, wherein the second in-operation period correspondsto an in-manipulation time during which the user inputs to the imageprocessing apparatus, wherein, as to a login period specified by anauthentication log whose logout cause is specified to be timeout, thecalculation unit does not include a period necessary to the timeout intothe second in-operation period, and wherein the steps are executed by aprocessor.
 9. A non-transitory computer-readable storage medium storinga computer program for causing a computer to execute a method forcalculating an in-operation time of an image processing apparatus, themethod comprising: acquiring an authentication log including informationcapable of specifying login time and logout time of a login process inthe image processing apparatus; acquiring a job log includinginformation capable of specifying job start time and job end time of ajob processed by the image processing apparatus; and calculating thein-operation time of the image processing apparatus based on a firstin-operation period corresponding to a job processing period specifiedby the job log and a second in-operation period corresponding to aperiod other than a job processing period specified from a job logrelating to the authentication log, in a login period specified from theauthentication log, wherein the second in-operation period correspondsto an in-manipulation time during which the user inputs to the imageprocessing apparatus, and wherein, as to a login period specified by anauthentication log whose logout cause is specified to be timeout, thecalculation unit does not include a period necessary to the timeout intothe second in-operation period.